.com
Hosted by:
Unit testing expertise at your fingertips!
Home | Discuss | Lists

continuous integration

The agile software development practice of integrating software changes continuously. In practice, this means that developers integrate their changes every few hours to days. Continuous integration often includes the practice of an automated build that is triggered by each check in. The build process typically runs all the automated tests an may even run tests that aren't run before check in because they take too long. The build is considered to have "failed" if any tests fail. When the build fails, teams typically consider getting the build working again to be the top priority; only code changes aimed at fixing the build are allowed until a successful build has occured.



Page generated at Wed Feb 09 16:39:10 +1100 2011

Copyright © 2003-2008 Gerard Meszaros all rights reserved

All Categories
Introductory Narratives
Web Site Instructions
Code Refactorings
Database Patterns
DfT Patterns
External Patterns
Fixture Setup Patterns
Fixture Teardown Patterns
Front Matter
Glossary
Misc
References
Result Verification Patterns
Sidebars
Terminology
Test Double Patterns
Test Organization
Test Refactorings
Test Smells
Test Strategy
Tools
Value Patterns
XUnit Basics
xUnit Members
All "Glossary"
acceptance test
accessor
ACID
agile method
annotation
anonymous inner class
anti-pattern
API
aspect-oriented programming
assertion
asynchronous test
attribute
back door
BDUF
behavior smell
behavior-driven development
black box
block closure
block
boundary value
built-in self test
business logic
class attribute
class method
class variable
closure
code smell
component test
component
constructor
continuous integration
control point
customer test
data access layer
depended-on component (DOC)
design for testability
design pattern
developer test
DFT
direct input
direct output
document-driven development
domain layer
domain model
DTO
dynamic binding
EDD
emergent design
endoscopic testing
entity object
equivalence class
example-driven development
exercise SUT
expectation
expected outcome
exploratory testing
eXtreme Programming
factory
false negative
false positive
fault insertion test
feature
FIT test
fixture holding class variable
fixture holding instance variable
fixture holding local variable
fixture setup
fixture teardown
fixture
fixture
fluent interface
front door
function pointer
functional test
garbage collection
global variable
green bar
GUI
happy path
Hollywood Principle
IDE
incremental delivery
incremental development
indirect input
indirect output
inner class
instance method
instance variable
interaction point
interface
inversion of control
IOC
iterative development
layer-crossing test
legacy software
liveware
local variable
manual test
meta object
metatest
method attribute
mixin
module
need-driven development
object-relational mapping
observation point
ORM
outgoing interface
pattern language
pattern
per-functionality test
polymorphism
presentation layer
presentation logic
procedure variable
production code
production
programmer test
project smell
pull
red bar
refactoring
reflection
regression test
result verification
retrospective
root cause analysis
round trip test
service object
setter
smell
spike
stateless
static binding
static method
static variable
STDD
story test
story
storytest-driven development
STTCPW
substitutable dependency
SUT
synchronous test
task
TDD
test automater
test case
test code
test condition
test context
test database
test debt
test driver
test driving
test error
test failure
test fixture
test fixture
test fixture
test maintainer
test package
test reader
test result
test run
test smell
test stripper
test success
test suite
test-driven bug fixing
test-driven development
test-first development
test-last development
test-specific equality
test
UML
unit test
use case
user acceptance test
user story
verify outcome